Subject: appnLsMaxSendBtuSize

From: "R.E. (Robert) Moore (254-4436)" <[email-masked]>
Date: Wed, 31 Jan 96 10:24:42 EST

In editing the APPN MIB, I've updated this object like this:

appnLsMaxSendBtuSize OBJECT-TYPE
      SYNTAX INTEGER (99..32767)
      UNITS "bytes"
      MAX-ACCESS read-only
      STATUS current
      DESCRIPTION
           "Numeric value between 99 and 32767 inclusive indicating the
           desired number of bytes in a Basic Transmission Unit (BTU)
           that can be sent on this TG.  This is an administratively
           assigned value.

           The maximum BTU size for the TG is the smaller of this value
           and the partner's maximum receive BTU length, received in
           XID."

      ::= { appnLsEntry 16 }

Several points I wanted to run by people:

1.  We had talked about making this object an OCTET STRING, as we did for
    the TG delay and effective capacity objects.  However, when this
    value flows in an XID, there's nothing unique about the encoding:
    it's just a 15-bit hex value.  Thus there's no reason to do the OCTET
    STRING trick here.

2.  The 99-byte minimum value is in fact part of the APPN architecture,
    so I've reflected that in the object.

3.  Here's the one I'm not sure of.  Based on the DESCRIPTION text as it
    was before, I've added the second paragraph, to indicate clearly that
    this object represents this node's starting point for max outbound
    BTU size for this TG, *not* the final value that takes into account
    what the other end can receive.  Is this correct, or was this object
    supposed to return the final value for the TG?

Thanks,
Bob Moore
IBM Network Management Architecture

---

From: "Mark C. Regan" <[email-masked]>
Date: Tue, 13 Feb 96 7:21:40 PST

Bob,

I disagree with #3 below.  I think the object should
display configured values when inactive/activating
and negotiatated values when active.  This provides a much
more useful object that way.  Not to mention that we've
set the precedent in other objects where the values 
change with the states.

Also, in the description, we should use 'link', not 'TG',
since we are in the link table.

Sound good?  Mark
> IBM Network Management Architecture

--------------------------------------------
Mark C. Regan       
Cisco Systems, Inc. 
(770) 984-2867

---

From: Bob Clouston <[email-masked]>
Date: Tue, 13 Feb 96 10:33:46 EST

I agree with you.  You'll put this on the mailer?